Readme for Test Management Environment
Quantum Data, Inc.

------------------------------------------------
 1. Installation
------------------------------------------------
Installation of the TME is performed by unzipping the provided
zip file (TME_1345.zip) to a directory of your choice.  The TME does
not require that it be run from a certain directory.  For Windows
users, we also provide a self-extracting executable file for your
convenience.

NOTE: To use serial ports on the TME tool, you must use
javacomm20-win32.zip (or a similar version for your platform)
and place the library in your Java VM's library path.  We provide
javacomm20-win32.zip for you in the JavaLibs directory.

------------------------------------------------
 2. Running the TME
------------------------------------------------
The TME is run through any platform that can run executable Java
JAR files.  For Windows machines, this will be set up for you
upon installation of the Java Runtime Environment (JRE).  To
run the TME, simply double-click on the file TME.jar in the
directory that was created in step 1.  The TME will be displayed
shortly after.

To manually run the TME through a command-line Java runtime, enter
> java -jar TME.jar
from the TME's main folder.

The TME requires a resolution of 800x600 or higher, and Java 5.0 (1.5).

------------------------------------------------
 3. Using the TME
------------------------------------------------
To run the TME, please follow these important steps:

- Set up a connection to the generator from the Host menu.  The
Host menu can be accessed using the bar at the bottom of the
screen.  Once there, you will see various connection types
available to you.  Currently, an ethernet connection for maximum
flexibility.  Setting up an ethernet connection is performed by
selecting an ethernet entry in the Host menu and inputting an IP
address.  Once the IP address is added, press Test and the
connection will be tested to see if it is able to interface with
the TME.

- Next, before entering a tool, you will need to use or define a
unit to perform tests upon.  This is done using the upper menu bar.
The bar is organized such that the user should select or create a
unit from a product type, and then from a model type, and lastly,
the unit itself.  The first step will be to go into the Select
Model menu and select a product, and then select or create and
model.  Models are filtered based upon the product type decision.
If you would like to create a new model, simply select an existing
base model to copy, and press "Duplicate As".  Once you have
selected a model, you will be automatically brought to the Select
Unit menu.  You can retest an old unit or create a new one using
the method described in the Select Model menu.

- Once you have a unit selected, you may begin testing.  The TME
will automatically bring the user to the first test suite available.
When other tools become available, they will be selectable from the
right-hand menu.  If you have created a new model, you must enter
the Declare tab and enter the CDF values for the new model (making
sure to press "Finish" at the end).  The Test tab provides an
intuitive method of proceeding through the compliance test.  To
begin the first test, simply use the "Step >" button to step
through the test.  Once the test is complete, the tester will be
provided with a result for the test.  To continue with the tests,
press "Test >".

- When testing has completed, the user may want to view the reports
of the tests, or print or save a hard copy of the results.  This
capability is provided through the "Report" menu.  From here, you
may view any single test's results, or, if you press "HardCopy",
you will be given a complete test result to view.  This can be
printed from the tool's user interface, or saved as an HTML file
for later viewing or printing.

------------------------------------------------
 4. Release Notes / Errata
------------------------------------------------
Version 1.345
- Fixed behavior of 11.1.4-12 (missing potential check)

Version 1.344
- Fixes behavior of 11.1.15-1 (missing step)

Version 1.343
- Fixes behavior of test 9.3-4 when DUT does not stop sending.

Version 1.342
- Fixes CDF mappings for tests 9.6-1, 9.6-2 and 11.1.7-1

Version 1.341 (Beta)
- Implements needed changes for 11.1.15-1 to have the proper <Active Source> when queried

Version 1.34
- Fixed minor CDF to test mapping issue (affects tests 11.1.13-5, 11.2.7-10 and 11.2.7-11)
- Modified TME base code to add new CDF entries to old CDFs

Version 1.331
- Updated to HDMI 1.3c (removed tests 11.1.1-6 and 11.1.1-7)
- Fixed CDF to test mapping issues
- Modified 9.4-1 for <Vendor Command with ID> to ensure missing bytes
- Removed <Vendor Command> test section from 9.4-1 because <Vendor Command> could be 0 bytes

Version 1.33
- Fixed case when user enters exactly 3.26 or 3.34 in CECT 7 tests
- Fixed 11.2.9-2 step ordering
- Fixed mandatory status of <Power Status> for Playback Devices
- Improved retry detection in CECT 9.3
- Adds missing test 11.2.6-2 for LA=0

Version 1.324 (Unreleased)
- Allowed bus monitoring to be enabled at the beginning of the test.

Version 1.323
- Fixed 11.1.13-5 appearance issue
- Fixed 9.6-2 showing up when no HDMI outputs exist
- Fixed minor step order issue with some DUTs

Version 1.32
- Fixed bus monitor clearing issues in 9.3
- Improved testing reliability in cases where unexpected messages are likely
- Improved timing of message conversations
- Resolved many physical addressing issues
- Improved responses to new opcodes (audio opcodes in particular)
- Added <Image View On> message at the end of each standby test in order to attempt to awaken the TV DUT
- Added notes to resolve some CDF mapping ambiguity
- Fixed <User Control Pressed> tests to not mandate a single message be sent (not required by CTS)
- Fixed mandatory capabilities of CDF

Version 1.31
- Improved retry count checks in CECT 9.3
- Improved wording about "child positions"
- Improved wording about channel identification

Version 1.30
- Implemented HDMI 1.3A CTS tests
- Allowed for switching of Auto-Step mode
- Further improvements of the CDF system
- Fixed some more issues with unexpected messages

Version 1.20
- Enhanced menu operation
- Less user involvement required to run test
- Verified to work under Mac OS X, Linux and Windows 2000/XP
- Fixed more CDF test mapping issues
- Improved test flow
- Fixed known issues with unexpected message handling

Version 1.10
- Fixed some CEC CDF -> test mapping issues
- Fixed EDID compatibility for release 2.2.3+
- Removed serial ports from Host menu
- Simplified some menus
- Fixed some network connection issues
- Verified/improved support for cross-platform use

Version 1.00:
- First public release

------------------------------------------------
 5. Disclaimer
------------------------------------------------
This tool is provided without warranty.  Quantum Data assumes no
responsibility for any damage to equipment or data caused directly
or indirectly by the usage of this tool.  Furthermore, by using this
tool, you agree to not hold accountable Sun Microsystems, Apache,
and the authors of JUnit, and agree to their license agreements.